-
-
Notifications
You must be signed in to change notification settings - Fork 167
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OSS-Fuzz Integration #569
OSS-Fuzz Integration #569
Conversation
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
Hi, thanks for the PR. To merge it I would like the tests to run. E.g. can you create a changelog entry? I wonder why the other tests fail. |
The other tests fail with
It might be needed to either install the dependency or exclude the fuzzing test file from being collected when we test the documentation. Either is fine. |
@niccokunzmann Hey Nicco, I added a changelog entry and omitted the fuzzing directory from the doctest! Thank you! |
Thanks! I am a bit confused not seeing the other tests run also. This might not be your code though... I am investigating... #571 |
#573 is a follow-up pull request that also does not distribute the fuzzing files. |
Thank you so much Jaca!!On Oct 25, 2023, at 12:25 PM, Jaca ***@***.***> wrote:
Merged #569 into master.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Thank you so much Nicco! Really appreciate your help with getting this situated :) I will keep you posted as to what, if anything, is uncovered. Thank you again! On Oct 25, 2023, at 7:28 AM, Nicco Kunzmann ***@***.***> wrote:
#573 is a follow-up pull request that also does not distribute the fuzzing files.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Hello,
This is a follow-on from my Issue regarding OSS-Fuzz integration. This PR introduces the source for the fuzzer and a YAML config to fuzz each PR for a set duration. I would greatly appreciate it being merged in!
I will continue monitoring OSS-Fuzz for bugs and fix any I can in future PRs. Max M also has access to the OSS-Fuzz dashboard to review any security-relevant crashes that may come up.
Please let me know if anything else is needed.
Thank you!